➜ uname -r
# get installed kernel version
➜ pacman -S linux-headers
# select kernel version
| #include <iostream> | |
| #include <vector> | |
| #include <algorithm> | |
| // функція для додавання | |
| int add(int a, int b) { | |
| return a + b; | |
| } | |
| // функція для віднімання |
➜ uname -r
# get installed kernel version
➜ pacman -S linux-headers
# select kernel version
If you're encountering ping github.com failing inside WSL with a Temporary failure in name resolution, you're not alone — this has been a long-standing issue, especially when using VPNs or corporate networks.
This issue is now fixed robustly with DNS tunneling, which preserves dynamic DNS behavior and avoids limitations like WSL’s former hard cap of 3 DNS servers in /etc/resolv.conf.
DNS tunneling is enabled by default in WSL version 2.2.1 and later, meaning that if you're still seeing DNS resolution issues, the first and most effective fix is simply to upgrade WSL. Upgrading WSL updates the WSL platform itself, but does not affect your installed Linux distributions, apps, or files.
To upgrade WSL, follow these steps,
| Filter | Description | Example |
|---|---|---|
| allintext | Searches for occurrences of all the keywords given. | allintext:"keyword" |
| intext | Searches for the occurrences of keywords all at once or one at a time. | intext:"keyword" |
| inurl | Searches for a URL matching one of the keywords. | inurl:"keyword" |
| allinurl | Searches for a URL matching all the keywords in the query. | allinurl:"keyword" |
| intitle | Searches for occurrences of keywords in title all or one. | intitle:"keyword" |
| --- | |
| name: frontend-design | |
| description: Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics. | |
| license: Complete terms in LICENSE.txt | |
| --- | |
| This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices. | |
| The user provides frontend requirements: a component, page, application, or interface to build. They may include context about the purpose, audience, or technical constraints. |
| /* | |
| ```_____````````````_````_`````````````````_``````````````_```````````` | |
| ``/`____|``````````|`|``|`|```````````````|`|````````````|`|``````````` | |
| `|`|`````___```___`|`|`_|`|__```___```___`|`|`__```````__|`|`_____```__ | |
| `|`|````/`_`\`/`_`\|`|/`/`'_`\`/`_`\`/`_`\|`|/`/``````/`_``|/`_`\`\`/`/ | |
| `|`|___|`(_)`|`(_)`|```<|`|_)`|`(_)`|`(_)`|```<```_``|`(_|`|``__/\`V`/` | |
| ``\_____\___/`\___/|_|\_\_.__/`\___/`\___/|_|\_\`(_)``\__,_|\___|`\_/`` | |
| ``````````````````````````````````````````````````````````````````````` | |
| ``````````````````````````````````````````````````````````````````````` | |
| */ |
This will allow you to have one device (ex computer/laptop) that has a bluetooth device, and you want to connect two headphones and share the same audio.
tl;dr: Wayland is not "the future", it is merely an incompatible alternative to the established standard with a different set of priorities and goals.
Wayland breaks everything! It is binary incompatible, provides no clear transition path with 1:1 replacements for everything in X11, and is even philosophically incompatible with X11. Hence, if you are interested in existing applications to "just work" without the need for adjustments, then you may be better off avoiding Wayland.
Wayland solves no issues I have but breaks almost everything I need. Even the most basic, most simple things (like xkill) - in this case with no obvious replacement. And usually it stays broken, because the Wayland folks mostly seem to care about Automotive, Gnome, maybe KDE - and alienating e
The always enthusiastic and knowledgeable mr. @jasaltvik shared with our team an article on writing (good) Git commit messages: How to Write a Git Commit Message. This excellent article explains why good Git commit messages are important, and explains what constitutes a good commit message. I wholeheartedly agree with what @cbeams writes in his article. (Have you read it yet? If not, go read it now. I'll wait.) It's sensible stuff. So I decided to start following the
| from Crypto.Hash import SHA256 | |
| from Crypto.PublicKey import ECC | |
| from Crypto.Signature import DSS | |
| from urllib.parse import urlparse | |
| import re | |
| import json | |
| import requests | |
| import datetime | |
| import base64 | |
| import sys |